home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++,comp.os.ms-windows.misc
- Subject: Re: Borland C++ versus Visual C++
- Date: 18 Apr 1996 20:34:54 GMT
- Organization: Borland International
- Message-ID: <4l691e$san@druid.borland.com>
- References: <4ksiob$537@head.globalcom.net> <3175B93A.377E@cedarnet.com> <31766392.39D@airmail.net>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <31766392.39D@airmail.net>, ebarb@airmail.net says...
- >
- >Jeff Coil wrote:
- >> One more thing.....I have met many "compiler bashers" on both sides and
- >> have found most of them haven't even used the competitors product, It
- >> must be easier to bash it than learn it.
- >
- >I'll freely admit that I haven't used Borland C++ since v4.0. When I
- discovered
- >that the IDE compiler and the command line compiler generated different code
- >(tested using the same makefile!) I decided not to wait for Borland to
- econcile
- >the two and completely bailed out of Borland.
- >
-
- Since the IDE does not use makefiles, there's clearly something missing in
- this description.
-
- >One would think that they'd have just the one compiler (like everybody else).
-
- The IDE and the command-line use the same compiler and always have.
-
-